Skip to content

Adds table to dynamic tag logic explanation #1749

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

szabosteve
Copy link

@szabosteve szabosteve commented Aug 18, 2025

Overview

This PR adds a table to the section that explains the logic of dynamic badges for better understanding.

@szabosteve szabosteve added the documentation Improvements or additions to documentation label Aug 18, 2025
Copy link

🔍 Preview links for changed docs

@szabosteve szabosteve marked this pull request as ready for review August 18, 2025 11:28
@szabosteve szabosteve requested review from a team as code owners August 18, 2025 11:28
@@ -8,7 +8,7 @@ Specifically for versioned products, badges will display differently when the `a
* `Deprecation planned` (if the lifecycle is deprecated)

Example: {applies_to}`stack: deprecated 99.99`
* `Removal planned` (if the lifecycle is removed)
* `Removal planned` (if the lifecycle is removed)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd remove these bullets in favor of the table below + kind of rework the content so it's introducing the table instead


| Lifecycle | Release status | Badge text |
|-------------|----------------|-----------------------------------------------------------------------------------|
| preview | prerelease | Planned |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these can have examples too. just set the version to 99.99

Comment on lines 18 to 20
:::{note}
Visuals and wording in the output documentation are subject to changes and optimizations.
:::
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd also move this note down to the bottom

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants